home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19980901-19981211
/
000341_news@newsmaster….columbia.edu _Wed Nov 25 00:35:43 1998.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
4KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id AAA21897
for <kermit.misc@watsun.cc.columbia.edu>; Wed, 25 Nov 1998 00:35:42 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id AAA02432
for kermit.misc@watsun; Wed, 25 Nov 1998 00:35:42 -0500 (EST)
Path: news.columbia.edu!panix!howland.erols.net!wn3feed!worldnet.att.net!135.173.83.225!attworldnet!newsadm
From: "Joseph L. Kaiser" <jlkaiser@ouray.cudenver.edu>
Newsgroups: comp.protocols.kermit.misc,de.alt.comm.mgetty
Subject: Re: At Wit's End on system freezes
Date: 25 Nov 1998 05:35:33 GMT
Organization: AT&T WorldNet Services
Lines: 79
Message-ID: <365B9709.212BF3F3@ouray.cudenver.edu>
References: <365ACCF8.1C502662@ouray.cudenver.edu> <73em90$6ch$1@apakabar.cc.columbia.edu>
NNTP-Posting-Host: 12.74.90.212
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.04 [en] (Win95; U)
To: Frank da Cruz <fdc@watsun.cc.columbia.edu>
Xref: news.columbia.edu comp.protocols.kermit.misc:9548 de.alt.comm.mgetty:8216
Frank da Cruz wrote:
: The history of the problem is this. We upgraded to RedHat 4.2 and a new
> : ethernet network. The modems were attached to the serial ports of the
> : nodes of the network (4) for various and sundry reasons. The system
> : would freeze/crash so that I would have to reboot anywhere about every
> : 3-10 days. We pulled the modems in July and put them all on the
> : Rocketport on the main server. The system began to freeze about 1-5
> : times a day and I had to reboot that often. I started to rule things
> : out. I obtained the latest and greatest RocketPort driver. The
> : behavior stayed the same. I played with the initialization strings in
> : mgetty and the behavior stayed the same.
> :
>
> This is a critical area. There might very well be a setting that makes
> the problem go away, but you didn't hit upon it in your experimentation.
> For example, did you try all possible DSR-behavior selections? (&S0,
> &S1, &S2, ...)
>
No, I could try this...
> : In the middle of all this, I
> : discovered that if I turned on and off the offending modem my system
> : "unfroze" without rebooting. This saved a lot of time and frustration
> : for all concerned.
> :
> Because it resets the modem to its factory or saved state, which agrees
> with what mgetty and the port drivers need.
>
> : I then sought to find out what made a modem an
> : offending modem. It appears to boil down to Kermit file transfers.
> :
> What else are you using the modems for besides Kermit transfers?
Nothing other then kermit transfers and the occasional at home user.
> : Sometimes when the script is restarted and the modem is then accessed
> : the system freezes, as if the modem is already being used but no lock
> : file exists.
> :
>
> When you say "the system freezes", do you mean the entire system, or do you
> mean the process that is trying to open the modem? If you mean the whole
> system, then there is a serious problem in the system itself, since no
> user program should be able to freeze Linux.
>
When I say "the system freezes" I mean the entire systems stops. The modem lights
cease to move, I can't toggle windows on the main server or any of the nodes of
the network, there is no logging in there is no logging out, all processes stop
whether on the server or on the nodes. From what you and Gert are saying this is
starting to sound like a hardware problem, isn't it? Or possibly a network
configuration problem. I "inherited" this system from a previous systems
administrator who did all the initial set up of the network. Not having the
knowledge to properly assess his work in this matter I have let it go. Perhaps I
need to check everything.
Thanks to both you and Gert. I have plenty to start testing. If this is sounding
to your minds like a hardware problem or some kind of configuration problem,
please let me know.
Also, in response to setting the hangup method to rs232, I already do that, one of
the first things I tried. and the modem is already set for &D2. But I will
definitely try using the generic modem.
Thanks much,
Joe Kaiser